Method and system for automatic configuration of a communications interface for a specialized data network of an aircraft

ABSTRACT

A method of automatic configuration of a communications interface of an unknown data network, the method comprising connecting an Electronic Flight Bag (EFB) to the unknown data network, attempting to open communication ports, in response to attempting to open communication ports, receiving data from the unknown data network, determining, by a controller module, if the selected communications interface can interpret the received data, and operating the communications interface of the EFB in accordance with the selected communications interface.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application claims priority to and benefit of U.S. ProvisionalPatent Application No. 62/926,809, filed Oct. 28, 2019, which isincorporated herein in its entirety.

TECHNICAL FIELD

This disclosure relates generally to interfacing a device forcommunication between the device and an unknown avionics-specific datanetwork.

BACKGROUND

For contemporary aircraft, an avionics ‘platform’ includes of a varietyof elements such as sensors, data concentrators, a data communicationsnetwork, radio frequency sensors and communication equipment,computational elements, operational or functional elements, andgraphical displays. These components can share information with othercomponents over the data communications network.

Transfer of data to and from components, or over the data communicationsnetwork, can utilize specialized data networks, such as AeronauticalRadio Inc. (ARINC) compliant data networks, and can define standards orspecifications for network operations, including data transmissions.Different aircraft or avionics platforms can further utilize differentspecialized data networks, or utilize a combination of differentspecialized data networks. Network components utilized to construct thedata network can utilize a specialized data network protocol, hardwareincluding relays, switches, communicative connections, and the like, toensure performance of the network architecture for the specialized data,or under the performance of the network communications defined byvarious data network specifications.

BRIEF DESCRIPTION

In one aspect, the present disclosure relates to a method of automaticconfiguration of a communications interface of an unknown data network,the method including connecting an Electronic Flight Bag (EFB) to theunknown data network, attempting to open communication ports of theunknown data network based on known communications data libraryconfigurations for a known set of data networks, defining a selectedcommunications interface, in response to attempting to opencommunication ports, receiving data from the unknown data network,determining, by a controller module, if the selected communicationsinterface can interpret the received data, and upon successfulinterpretation of the received data, operate the communicationsinterface of the EFB in accordance with the selected communicationsinterface.

In another aspect, the present disclosure relates to a communicationsdevice for communicating with an unknown avionics specific data network,including a communications interface, a communication data librarystored in memory and defining a set of known communication interfaceconfigurations for communicating with a predetermined set of datanetworks, and a controller module. The controller module is configuredto, upon connection of the communications interface with an unknownavionics specific data network, select a known communication interfaceconfiguration, attempt to open communication ports of the unknown datanetwork based on the selected known communication interfaceconfiguration, receive data from the unknown data network, determine ifthe selected known communication interface configuration can interpretthe received data, and upon successful interpretation of the receiveddata, operate the communications interface in accordance with theselected known communication interface configuration.

These and other features, aspects and advantages of the presentdisclosure will become better understood with reference to the followingdescription and appended claims. The accompanying drawings, which areincorporated in and constitute a part of this specification, illustrateaspects of the disclosure and, together with the description, serve toexplain the principles of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a top down schematic view of an example aircraft and avionicsdata network architecture of an aircraft, in accordance with variousaspects described herein.

FIG. 2 is a schematic view of an example avionics data network of FIG. 1, in accordance with various aspects described herein.

FIG. 3 is a schematic view of an example avionics data networkingdefining communication between an Electronic Flight Bag (EFB) and anavionics system, in accordance with various aspects described herein.

FIG. 4 is schematic system view of the communication between the EFB andthe avionics system of FIG. 3 , in accordance with various aspectsdescribed herein.

FIG. 5 is a flow chart diagram showing a method of configuringcommunications between a device and an avionic system in a specializeddata network, in accordance with various aspects described herein.

DETAILED DESCRIPTION

Aspects of the disclosure described herein are provided with respect toa specialized avionics data protocol, but it will be understood that theapparatus and method described herein can be implemented in anyenvironment using a data communications network interconnecting a set ofdata-generating components or devices with a set of data-consumingcomponents or avionics systems, computers, or the like. Aspects of thedisclosure can include data communications networks configured tooperate according to defined network characteristics or specifications.For example, contemporary aircraft operate a set of componentsinterconnected by way of a data network defined by a network standard,such as the ARINC, or a subdivision thereof, for example ARINC 429(A429) specification, ARINC 664 (A664), Ethernet, or the like, which areincorporated herein in their entirety. Furthermore, while theaforementioned examples can include network topology examples,application level protocol standards, including but not limited to,ARINC 702A (A702A), ARINC 834 (A834), or the like, can be included intheir entirety. While aspects of the disclosure refer to the ARINC-basedspecifications, aspects of the disclosure are applicable to otherspecialized data networks, or the like utilized for data transmissionsbetween a set of interconnected data sources and data destinations.

Furthermore, as used herein, the term “set” or a “set” of elements canbe any number of elements, including only one. Also, as used herein,while sensors can be described as “sensing” or “measuring” a respectivevalue, sensing or measuring can include determining a value indicativeof or related to the respective value, rather than directly sensing ormeasuring the value itself. The sensed or measured values can further beprovided to additional components. For instance, the value can beprovided to a controller module or processor, and the controller moduleor processor can perform processing on the value to determine arepresentative value or an electrical characteristic representative ofsaid value.

All directional references (e.g., radial, axial, upper, lower, upward,downward, left, right, lateral, front, back, top, bottom, above, below,vertical, horizontal, clockwise, counterclockwise) are only used foridentification purposes to aid the reader's understanding of thedisclosure, and do not create limitations, particularly as to theposition, orientation, or use thereof. Connection references (e.g.,attached, coupled, connected, and joined) are to be construed broadlyand can include intermediate members between a collection of elementsand relative movement between elements unless otherwise indicated. Assuch, connection references do not necessarily infer that two elementsare directly connected and in fixed relation to each other. Innon-limiting examples, connections or disconnections can be selectivelyconfigured to provide, enable, disable, or the like, an electricalconnection or communicative connection between respective elements.Additionally, as used herein, “electrical connection” or “electricallycoupled” can include a wired or wireless power or data (e.g.communicative or transmissive) connection between respective components.

Additionally, as used herein, a “controller” or “controller module” caninclude a component configured or adapted to provide instruction,control, operation, or any form of communication for operable componentsto affect the operation thereof. A controller module can include anyknown processor, microcontroller, or logic device, including, but notlimited to: Field Programmable Gate Arrays (FPGA), anApplication-Specific Integrated Circuit (ASIC), a full authority digitalengine control (FADEC), a Proportional controller (P), a ProportionalIntegral controller (PI), a Proportional Derivative controller (PD), aProportional Integral Derivative controller (PID controller), ahardware-accelerated logic controller (e.g. for encoding, decoding,transcoding, etc.), the like, or a combination thereof. Non-limitingexamples of a controller module can be configured or adapted to run,operate, or otherwise execute program code to affect operational orfunctional outcomes, including carrying out various methods,functionality, processing tasks, calculations, comparisons, sensing ormeasuring of values, or the like, to enable or achieve the technicaloperations or operations described herein. The operation or functionaloutcomes can be based on one or more inputs, stored data values, sensedor measured values, true or false indications, or the like.

While “program code” is described, non-limiting examples of operable orexecutable instruction sets can include routines, programs, objects,components, data structures, algorithms, etc., that have the technicaleffect of performing particular tasks or implement particular abstractdata types. In another non-limiting example, a controller module canalso include a data storage component accessible by the processor,including memory, whether transient volatile or non-transient, orNon-Volatile Memory (NVM). Additional non-limiting examples of thememory can include Random Access Memory (RAM), Read-Only Memory (ROM),flash memory, or one or more different types of portable electronicmemory, such as discs, DVDs, CD-ROMs, flash drives, universal serial bus(USB) drives, the like, or any suitable combination of these types ofmemory. In one example, the program code can be stored within the memoryin a machine-readable format accessible by the processor. Additionally,the memory can store various data, data types, sensed or measured datavalues, inputs, generated or processed data, or the like, accessible bythe processor in providing instruction, control, or operation to affecta functional or operable outcome, as described herein.

In another non-limiting example, a control module can include comparinga first value with a second value, and operating or controllingoperations of additional components based on the satisfying of thatcomparison. For example, when a sensed, measured, or provided value iscompared with another value, including a stored or predetermined value,the satisfaction of that comparison can result in actions, functions, oroperations controllable by the controller module. As used, the term“satisfies” or “satisfaction” of the comparison is used herein to meanthat the first value satisfies the second value, such as being equal toor less than the second value, or being within the value range of thesecond value. It will be understood that such a determination may easilybe altered to be satisfied by a positive/negative comparison or atrue/false comparison. Example comparisons can include comparing asensed or measured value to a threshold value or threshold value range.

The exemplary drawings are for purposes of illustration only and thedimensions, positions, order and relative sizes reflected in thedrawings attached hereto can vary.

As illustrated in FIG. 1 , an aircraft 10 can include at least onepropulsion engine, shown as a left engine system 12 and right enginesystem 14. The aircraft 10 can further include one or more data sources,that is, components that create, originate, or otherwise generate data,and data destinations, that is, components that receive, consume,process, or otherwise act on or effect an outcome or operation based ondata received. As shown, the aircraft 10 can include one or moreavionics system 18, including, but not limited to data storage orprocessing units, or functional systems such as the Flight ManagementSystem (FMS) or autopilot system, and a set of fixed aircraftcomponents, such as Line-Replaceable Units (LRUs) 21, networking endnodes, or modular components of a vehicle or aircraft.

Additional communicative devices can be included and connectable withthe aircraft 10, and can include, but is not limited to, a ConnectedFlight Management System (CFMS) or EFB operational aspects, functionaloperations, or the like. FIG. 1 illustrates a representative EFB 20 asone non-limiting example. The CFMS or EFB 20 can include moveable,mobile, or otherwise removable devices that are adapted or configured tocommunicate with the aircraft 10, avionics system 18, LRUs 21, or thelike, by way of a series of transmission pathways 22, network relays, ornetwork switches 16 (collectively, a “network mesh”). In contrast, theavionics system 18, and the LRUs 21 can include stationary data sources.As used herein, “stationary” denotes that the avionics system 18 or LRU21 can include devices that are generally fixed or incorporated into theaircraft 10 and would require significant work or maintenance servicesto remove from the aircraft 10, whereas “non-stationary” devices such asthe EFB 20 can include devices that can be moveable relative to theaircraft or data network, such as carried by one the flight crew fromone location to another either on, or off the aircraft 10. Non-limitingexamples of the EFB 20 can include a handheld device such as a tablet,palm-pilot, pager, portable computer, smart device, or the like, thatcan be carried onto the aircraft 10 by the flight crew. In contrast, astationary the avionics system 18 or LRU 21 can be, for example, acockpit display, cockpit computer, or the like. In another example, theEFB 20 can be stationary.

In the aircraft environment, the avionics system 18, or the EFB 20, thetransmission pathways 22, and the like, can be designed, configured, oradapted to operate according to a particular operation,interoperability, or form factor standards, such as those defined byARINC series standards. In the exemplary aspects illustrated, theavionics system 18 can be positioned near the nose, cockpit, or pilot ofthe aircraft 10 and the EFB 20 can be positioned near the nose, cockpit,or pilot of the aircraft 10, however, any relative arrangement can beincluded.

The avionics system 18 and EFB 20 can be configured to becommunicatively coupled by way of the series of transmission pathways22, network relays, or network switches 16. While network switches 16are schematically illustrated, non-limiting aspects of the disclosurecan be applied to peer-to-peer networks. The transmission pathways 22can include a physical connection between the respective components,such as a wired connection including Ethernet, or can include wirelesstransmission connections, including, but not limited to, WiFi (e.g.802.11 networks), Bluetooth, and the like. Collectively, the avionicssystem 18, EFB 20, transmission pathways 22, and switches 16 can form anavionics data network, or avionics-specific data network for theaircraft.

The aircraft 10, and the systems thereof, can be communicativelyinterconnected by way of the avionics-specific data network such has anARINC-compatible data network. The avionics-specific data network canbe, in one non-limiting example, an ARINC 429 (A429) compatible datanetwork. It will be appreciated that the aircraft 10, and the systemsthereof can be any avionics-specific data network compatible with anyARINC data network, including but not limited to an A664 data network,or any other known avionics-specific data network.

The EFB 20 can include, for example, entirely contained systems, radios,or other auxiliary equipment to manage or operate aircraft functions. Atleast a set of avionics system 18 or EFB 20 can, for example, generatedata, which can be modified, computed, or processed prior to, or inpreparation for packaging the data into data frames to be transmittedover the avionics data network by way of the transmission pathways 22 orswitches 16. At least another set of avionics system 18 or EFB 20 can,for example, consume the data transmitted over the avionics datanetwork. In some instances, a single avionics system 18 or EFB 20 canoperate to both generate and consume data. As used herein, “consume,”“consuming,” or “consumption” of data will be understood to include, butis not limited to, performing or executing a computer program, routine,calculation, or process on at least a portion of the data, storing thedata in memory, or otherwise making use of at least a portion of thedata.

The illustrated aircraft 10 is merely one non-limiting example of anaircraft 10 that can be used in aspects of the disclosure describedherein. Particularities of the illustrated aircraft 10 aspects,including relative size, length, number of engines, type of engines, andlocation of various components are not germane to the aspects of thedisclosure, unless otherwise noted.

FIG. 2 illustrates a non-limiting schematic view of a specialized datanetwork 24 according to aspects of the disclosure. The specialized datanetwork 24 can include various components, and perform the functions ofan avionics data network outlined herein. The specialized data networkcan include, but is not limited to, a set of redundant network switchingunits, such as a first set of switching units 26 defining a first pathand a second set of switching units 27 defining a second, or redundant,path. The first and second switching units 26, 27 collectively define anetwork mesh 28 for routing the transmission of data frames betweenrespective components, such as to and from the avionics system 18, andEFB 20 via the transmission pathways 22. As previously described, thetransmission pathways 22 can be any communicative pathway, including butnot limited to, wired or wireless communication connections. In onenon-limiting example, the network mesh 28 is further shown having a setof transmission pathways 22 between the network switching units 26, 27to provide redundancy in transmission pathways 22. In one non-limitingexample, the network mesh 28, the first set of switching units 26, thesecond set of switching units 27, or a combination thereof, can bearranged, configured, or otherwise enabled to utilize a specialized datanetwork 24 transmission schema. The aspects of the disclosureillustrated in FIG. 2 is merely one representation of the specializeddata network 24, and alternative configurations, organization, andcomponent quantities, including, but not limited to, avionics system 18,including but not limited to the EFB 20, LRUs 21, or network switchingunits 26, are envisioned.

FIG. 3 illustrates addition details of specialized data network 50, theEFB 20, and the avionic system 18. As used herein, the specialized datanetwork 50 can be similar to the specialized data network 24 of FIG. 2 .As shown, the EFB 20 can schematically include a controller module 52having a processor 54 and memory 56, and a set of communications librarydata 58 defining standards, rules, mechanisms, or other information ordata used or utilized to communicatively interface with the network mesh28 or avionics system 18, shown as an aircraft cockpit system 70. TheEFB 20 can further include an interface for communicating with thenetwork mesh 28, shown as a network interface 60. Non-limiting examplesof the network interface 60 can include hardware and softwareconfigurations adapted or configured to exchange, transmit, receive, orotherwise communicate with the network mesh 28 or other network nodesvia the transmission pathways 22. In one non-limiting example, thenetwork interface 60 can be based upon, or defined by, a standard or setof standards, such as an ARINC 759 (A759) hardware standard, an ARINC834 (A834) communications protocol standard, or a combination thereof.In one non-limiting example, the communications library data 58 can bestored in a memory, such as memory 56, of the EFB 20, and can includemultiple sets of standards, rules, mechanisms, or other information ordata used or utilized to communicatively interface with the network mesh28 or avionics system 18. For instance, a first set of standards, rules,mechanisms, or other information or data used or utilized tocommunicatively interface with the network mesh 28 or avionics system 18can be based upon the A429 standard, while a separate and distinctsecond set of standards, rules, mechanisms, or other information or datacan be based upon the A664 standard. In this sense, the communicationslibrary data 58 can define how the EFB is configured to or able tocommunicate or interface in accordance with different communication ordifferent specialized networks, by way of the network interface 60. Innon-limiting examples, the network interface 60 of the EFB 20 canoperating dynamically in accordance with at least a subset of thecommunication library data 58, that is, in accordance with differentsets of standards.

The aircraft cockpit system 70 is further illustrated to include aseparate Aircraft Interface Device (AID) 62 for communicating with thenetwork mesh 28, a redundant set of Communications Management Units(CMUs), shown as a first CMU 72 and a second CMU 74, and a redundant setof Flight Management Systems (FMSs), shown as a first FMS 76 and asecond FMS 78. In one non-limiting example, the AID 62 can include adevice that allows to bridge communication domains, standards, datatransmission, or the like, while implementing a domain guard forsecurity purposes.

During flight preparation and operations, a pilot can bring an EFB 20 onan aircraft 10, and can communicatively connect the EFB 20 with at leastone avionics system 18, such as an FMS 76, 78 of an aircraft cockpitsystem 70, by way of the specialized data network 50 (e.g. including thenetwork mesh 28). However, different aircraft 10 operate differentspecialized data networks 50 in accordance with current or legacyspecialized data network standards of communication. As such,interfacing the EFB 20 in such a way to be interoperable with differentcommunication standards can be difficult in an environment wherereprogramming or recertifying aircraft avionics systems 18 isundesirable due to costs of certification and testing.

Aspects of the disclosure can be included wherein the EFB 20, operatingin accordance with the disclosure, can be automatically registered andinterfaced with the network mesh 28, another avionics system 18, or thespecialized data network 50 of the aircraft 10, without specializedconfiguration or redesign, recoding, reprogramming, or replacement ofthe specialized data network 50 or avionics system 18.

As shown, upon connection of the EFB 20 with the network mesh 28 (e.g.via wired or wireless communication on the transmission pathways 22, thenetwork interface 60 can begin attempting to automatically determine oridentify the specialized data network 50 standards being utilized by theaircraft 10. The EFB 20 or the network interface 60 can include an autonetworking component 84 configured to or adapted to begin interfacingwith the network mesh 28 or specialized data network 50. In onenon-limiting example, the auto networking component 84 can includesecurity mechanisms to authorize communication between the EFB 20 andthe specialized data network 50, perform hardware or software“handshakes,” or the like, to achieve or adapt initial networkingprotocols in place. From there, the controller module (not shown) canoperate the network interface 60, the auto networking component 84, orthe EFB 20 to begin attempting to open known and predeterminedcommunication ports of the avionics system(s) 18 based on knowncommunications data library 58 configurations.

For example, the EFB 20 may attempt to open a first known communicationsport (e.g. a first transmission control protocol or “TCP” port) known tobe applicable in a first communications standard, such as an A664 port.If the attempt to open the A664 communications port, as defined by thecommunications data library 58 is successful, the EFB 20, the controllermodule, the communication data library 58, or the like can determine orotherwise make accounting that the EFB 20 is attempting to connect andcommunicate with an A664-based specialized data network 50. If theattempt to open the A664 communications port is unsuccessful, the EFB 20may attempt to open a different or a second known communications port(e.g. a second TCP port) known to be applicable in a secondcommunications standard, such as an A429 port, to determine if the EFB20 is attempting to connect and communicate with an A429-basedspecialized data network 50. The EFB 20 can continue attempting to openpredetermined communications ports, including but not limited to TCP orUser Datagram Protocol (UDP) ports in an attempt to identify, and thenconnect and communicate with, the specialized data network 50. Thus,aspects of the disclosure can be included wherein a single EFB 20 orCFMS can be communicatively connected with specialized data network 50,without special configuration or awareness of which or what specializeddata network 50 the aircraft is utilizing, so long as the specializeddata network 50 standards are included in the communications datalibrary 58.

FIG. 4 illustrate one non-limiting example of aspects of the disclosure.In the example of FIG. 4 , an avionics system 18 in the form of anaircraft cockpit system 70 is preconfigured to communicate with thespecialized data network 50 by way of an aircraft network interface 62operating under A429 and A834 network standards described herein (e.g.not limited to AID, network servers, routers, switches, or any functionoperating on like devices). Upon connection of the EFB 20 with thespecialized data network 50, the network interface 60 and autonetworking first connects with the specialized data network 50, and thenattempts to open communication ports of the specialized data network 50to determine which AID 62 or standards are utilized. The EFB 20illustrates a number of different data network interface standards 82available and defined within the communications data library 50. As usedherein, the set of data network interface standards 82 can include theapplication level protocols, as explained herein.

In one example, the EFB 20 can first attempt to open one or more A664communication ports of the specialized data network 50. Since thespecialized data network 50 is not operating in accordance with the A664specification, the opening or those ports or validation of communicationon those ports will fail. The EFB 20 can, for example, note the A664specification of the set of data network interface standards 82 is notapplicable (as shown by dotted outline denoting a “unselected” networkstandard 86). The process can then be repeated moving through otherpossible data network interface standards 82 until the correctlyselected data network interface standard 82 accomplishes or successfullyopens communications ports, as explained herein. The “selected” datainterface standards 88 are denoted by a solid outline, and match theavionics system 18 aircraft network interface 80 standards (e.g. notlimited to AID, network servers, routers, switches, or any functionoperating on like devices). As shown, the EFB 20 can include a similarprocess of opening communication ports and sequentially moving throughdata network interface standards 82 for both compatible receiving ofdata transmissions, as well as for compatible sending of datatransmissions. For examples, the A702A data network interface standard90 is shown as selected for sending data transmissions, separate andapart from determining the A429 and A834 data network interfacestandards 88 are selected for receiving data transmissions.

Once the suspected or selected data network interface standards 88 areidentified, non-limiting aspects of the disclosure can be includedwherein, for example, the EFB 20 receives a set of data transmissionstraversing the specialized data network 50, and attempts to interpret,decode, or otherwise facilitate use of the data transmissions in orderto validate or ensure the suspected or selected data network interfacestandards 88 are correct. For example, a failed attempted interpretationof the data transmission received by the EFB 20 can indicate theselected data network interface standard(s) 88 are incorrect, and thatthe EFB 20 will try to identify and connect with another or a differentnetwork interface standard 82. In contrast, a successful interpretationof the data transmission received by the EFB 20 can indicate or validatethat the selected data network interface standard(s) 88 is correct. If adetermination is made that the suspected or selected data interfacestandards 88 are correct (or otherwise, not determined they areincorrect), the EFB 20 can be operated in accordance with the selecteddata network interface standard(s) 88 to communicate with thespecialized data network 50 in accordance with the selected data networkinterface standard(s) 88. In this sense, the EFB 20 can then proceed tocommunicate with, for example, the first or second FMS 76, 78, or acombination thereof, in order to operate the aircraft 10. In anothernon-limiting example, The FMS 76, 78 can provide all the data itcontains to the last byte about how the flight plan looks like, however,the flight plan is limited to display it to the pilot per a fixed set ofrequirements of the display units. The fact that the FMS 76, 78 canreceive such a data structure enables EFB 20, applications thereon, orthe like, to display the data in novel ways that provide more insightsto the pilots on the status of the flight, departure or landingprocedures. Moreover, it can provide insights and alerts to the pilotsfor increased safety and better fuel efficiency. Also, the EFB 20 canedit, alter, or otherwise modify the route, flight plan, or otherparameters of the FMS 76, 78.

In one non-limiting example, the ordering of which to prioritize thedifferent network interface standard 82 attempts can be based upon alimited user-selectable input, or readable data of the aircraft orspecialized data networks thereon. In another non-limiting example,aspects of the disclosure can be applicable to automatically interfacewith a simulated avionics system environment, as opposed to an actual“real world” aircraft environment. In yet another non-limiting example,the communications library data 58 can library can either beinstantiated to identify the environment by itself or it can ask the AID62 (or any device in the aircraft 10 via the AID 62) to provide thecurrent configuration.

FIG. 5 illustrates a flow chart demonstrating a method 300 ofautomatically configuring an EFB 20 to communicate with an unknownspecialized data network 50. The method 300 begins by connecting the EFB20 to the specialized data network 50 at 310. Next, the EFB 20 attemptsto open communication ports of the avionics system 18 or the specializeddata network 50 based on known communications ports of the data networkinterface standards 82 of the communications data library 58configurations, at 320. Once the EFB 20 selects or suspects the datanetwork specification is correct, the EFB 20 can receive a set or subsetof data traversing the specialized data network, at 330. The EFB 20 canwork or attempt to interpret, decode, or otherwise facilitate use of thedata transmissions in order to validate or ensure the suspected orselected data network interface standards 88 are correct, at 340.Finally, if the suspected or selected data network interface standard 88is correct, the EFB 20 can be configured to operate in accordance withthe respective selected data network interface standard 88 tocommunicate with the specialized data network 50, at 350.

The sequence depicted is for illustrative purposes only and is not meantto limit the method 300 in any way as it is understood that the portionsof the method can proceed in a different logical order, additional orintervening portions can be included, or described portions of themethod can be divided into multiple portions, or described portions ofthe method can be omitted without detracting from the described method.For example, known communications ports or port ranges (e.g. multipleports) can be polled at the same time (e.g. simultaneously) to increaseresponse and setup time. In another example, once an initial set ofnetwork data is successfully decoded or validated, that data can containadditional information for configuration of the specialized datanetwork. In yet another example, the EFB 20 can utilize that additionalinformation for configuration to request additional information forconfiguration, or to validate the rest of the setup process hascompleted if further data is also successfully received.

Many other possible aspects and configurations in addition to that shownin the above figures are contemplated by the present disclosure.

The aspects disclosed herein provide a system adapted to automaticallyconfigure itself for communication by way of scanning the networkenvironment and selecting the network configuration that enablesinteraction to occur. The technical effect is that the above-describedaspects enables a device to communicate with an avionics network withoutknowledge of what communications standards the network utilizes, andwithout modifying the aircraft avionics on the network. One advantagethat can be realized in the above aspects is that the above describedaspects enables avoiding configuration and customization of differentinterfaces from different aircraft configurations. Pilots are nottypically trained in these technical environments, and not capable toreconfigure the environments in situ. By automating the process,development time is reduced in application programming for the EFB, andthe user experience remains high by the automated process. Additionally,with aspects of the disclosure, developers can avoid configuring oradapting EFBs on a per-airframe-basis. By implementing multiplecommunication library data sets, this solution is easier to debug andmaintain in a per-airframe-basis, and will be easier for developers todevelop limited applications despite a large number of differentaircraft in a fleet.

To the extent not already described, the different features andstructures of the various aspects can be used in combination with eachother as desired. That one feature cannot be illustrated in all of theaspects is not meant to be construed that it cannot be, but is done forbrevity of description. Thus, the various features of the differentaspects can be mixed and matched as desired to form new aspects, whetheror not the new aspects are expressly described. Combinations orpermutations of features described herein are covered by thisdisclosure.

This written description uses examples to disclose aspects of thedisclosure, including the best mode, and also to enable any personskilled in the art to practice aspects of the disclosure, includingmaking and using any devices or systems and performing any incorporatedmethods. The patentable scope of the disclosure is defined by theclaims, and can include other examples that occur to those skilled inthe art. Such other examples are intended to be within the scope of theclaims if they have structural elements that do not differ from theliteral language of the claims, or if they include equivalent structuralelements with insubstantial differences from the literal languages ofthe claims.

What is claimed is:
 1. A method of automatic configuration of acommunications interface of an aircraft data network, the methodcomprising: connecting an Electronic Flight Bag (EFB) to the aircraftdata network, the aircraft data network being one of a set of datanetworks defined by a communications data library defining acorresponding set of communications data library configurations;attempting to open communication ports of the aircraft data networkbased on one of the set of communications data library configurations,defining a selected communications interface; in response to attemptingto open communication ports, receiving data from the aircraft datanetwork; determining, by a controller module, if the selectedcommunications interface can interpret the received data; and uponsuccessful interpretation of the received data, operate thecommunications interface of the EFB in accordance with the selectedcommunications interface.
 2. The method of claim 1, further comprisingpre-loading the EFB with the set of communication data libraryconfigurations for the set of aircraft data networks.
 3. The method ofclaim 1, wherein the aircraft data network defines a specializedavionics data protocol.
 4. The method of claim 3, further comprisingoperating the communications interface of the EFB in accordance with atleast one ARINC-compliant avionics protocols.
 5. The method of claim 3wherein the selected communications interface can further include atleast one application-level protocol.
 6. The method of claim 5, furthercomprising operating the communications interface of the EFB inaccordance with at least one ARINC compliant application levelprotocols.
 7. The method of claim 1, wherein the aircraft data networkdefines a legacy network standard.
 8. The method of claim 1, furthercomprising determining if the selected communications interface caninterpret the received data by validating the received data.
 9. Themethod of claim 1, further comprising receiving a user-selectable inputat the EFB defining a user-selected input, and wherein attempting toopen communication ports of the aircraft data network is further basedon prioritizing at least one selected communications interfaceassociated with the user-selected input.
 10. The method of claim 9,wherein the user-selectable input includes multiple aircraft models. 11.The method of claim 1, wherein attempting to open communication portsincludes polling at least one of multiple communication portssimultaneously or a set of port ranges all at once.
 12. The method ofclaim 1, wherein operating the communications interface of the EFB inaccordance with the selected communications interface enables the EFB tocommunicate with at least one avionics system of an aircraft.
 13. Themethod of claim 12, wherein the at least one avionics system of theaircraft is a Flight Management System (FMS).
 14. The method of claim 1,further comprising, upon unsuccessful interpretation of the receiveddata, attempting to open communication ports of the aircraft datanetwork based another selected communications interface.
 15. Acommunications device for communicating with an avionics specific datanetwork, comprising: a communications interface; a communication datalibrary stored in memory and defining a set of communication interfaceconfigurations for communicating with a predetermined set of datanetworks; and a controller module configured to: upon connection of thecommunications interface with the avionics specific data network, selecta communication interface configuration; attempt to open communicationports of the avionics specific data network based on the selectedcommunication interface configuration; receive data from the avionicsspecific data network; determine if the selected communication interfaceconfiguration can interpret the received data; and upon successfulinterpretation of the received data, operate the communicationsinterface in accordance with the selected communication interfaceconfiguration.
 16. The communications device of claim 15, furthercomprising a user input, and wherein the controller module is furtherconfigured to attempt to open communication ports of the avionicsspecific data network further based on prioritizing a subset of thecommunication interface configurations associated with the user-selectedinput.
 17. The communications device of claim 16, wherein the user inputincludes a selectable list of aircraft models.
 18. The communicationsdevice of claim 15, wherein upon successful interpretation of thereceived data, the controller module is configured to operate thecommunications interface of the in accordance with the selectedcommunication interface configuration to communicate with at least oneavionics system of an aircraft.
 19. The communications device of claim18, wherein the at least one avionics system of the aircraft is an FMS.20. The communications device of claim 15, wherein the controller moduleis further configured to, upon unsuccessful interpretation of thereceived data, select another communication interface configuration andattempt to open communication ports of the avionics specific datanetwork based on the selected another communication interfaceconfiguration.